VIF: Fix out of bounds read caused by broken alignment logic - #14853
Open
chaoticgd wants to merge 1 commit into
Open
VIF: Fix out of bounds read caused by broken alignment logic#14853chaoticgd wants to merge 1 commit into
chaoticgd wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of Changes
Removes some broken alignment logic in nVifUnpack.
Rationale behind Changes
The correct way to align the value up would be
(size + 3) & ~0x3, not(size + 4) & ~0x3, but from checking around the code it seems like that logic isn't required anyway since the VU_Thread class makes sure everything is aligned itself.I was getting the following error while running PCSX2 under ASAN:
Suggested Testing Steps
Try a bunch of VU intensive games.
Did you use AI to help find, test, or implement this issue or feature?
I asked ChatGPT if it could see anything wrong with it after opening it, apart from that no.